Skip to content

Bugfix/safe clone deep #12388

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 14, 2025
Merged

Bugfix/safe clone deep #12388

merged 6 commits into from
May 14, 2025

Conversation

cscheid
Copy link
Collaborator

@cscheid cscheid commented Mar 26, 2025

Replaces cloneDeep with safeCloneDeep across our code base.

Because safeCloneDeep is better with types than cloneDeep, this also reveals some previous existing bugs and missing entries in our YAML schemas.

@cderv cderv added this to the v1.8 milestone Mar 31, 2025
@cderv
Copy link
Collaborator

cderv commented May 14, 2025

Is this ready to finalize this idea in all our codebase before we forget our previous discussion ?

That would be ideal.

@cscheid
Copy link
Collaborator Author

cscheid commented May 14, 2025

Agreed.

@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented May 14, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@cscheid cscheid merged commit 3a1d1ac into main May 14, 2025
49 checks passed
@cscheid cscheid deleted the bugfix/safe-clone-deep branch May 14, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants